Software Tag: Empirical Software Engineering Data for Traceability and Transparency of Software Project
نویسنده
چکیده
In this paper, we propose a scheme, named Software Tag, of software trade and development for improvement of traceability and transparency. Empirical data is collected during development, and processed into two types, open tag and secret tag, composing a software tag which is finally delivered to software purchaser.
منابع مشابه
Standardizing the Software Tag in Japan for Transparency of Development
In this paper, we describe the Software Tag which makes software development visible to software purchasers (users). A software tag is a partial set of empirical data about a software development project shared between the purchaser and developer. The purchaser uses the software tag to evaluate the software project, allowing them to recognize the quality level of the processes and products invo...
متن کاملA New Empirical Model to Increase the Accuracy of Software Cost Estimation (TECHNICAL NOTE)
We can say a software project is successful when it is delivered on time, within the budget and maintaining the required quality. However, nowadays software cost estimation is a critical issue for the advance software industry. As the modern software’s behaves dynamically so estimation of the effort and cost is significantly difficult. Since last 30 years, more than 20 models are already develo...
متن کاملSoftware Traceability: a Roadmap
ion and Traceability", Proceedings of the IEEE International Requirements EngineeringConference, Germany, September 2002. 70. Watkins R, Neal M, "Why and How of Requirements Tracing", IEEE Software, 104-106, July 1994
متن کاملA Requirements-to-Implementation Mapping Tool for Requirements Traceability
Software quality is a major concern in software engineering, particularly when we are dealing with software services that must be available 24 hours a day, please the customer and be kept permanently. In software engineering, requirements management is one of the most important tasks that can influence the success of a software project. Maintain traceability information is a fundamental aspect ...
متن کامل“But it Used to Meet the Requirements!” - Automated Satisfaction Assessment to Support Change
When software systems are in use, changes to requirements, design, and code are inevitable. Creating and preserving a requirements traceability matrix (RTM) for a particular software system documents shows how software artifacts are related, and, therefore, supports the impact assessment of potential changes as maintenance proceeds. Suppose that a particular software system completely implement...
متن کامل